-
Notifications
You must be signed in to change notification settings - Fork 39
DOCSP-47219 Midsync Reads FAQ #612
DOCSP-47219 Midsync Reads FAQ #612
Conversation
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
nvillahermosa-mdb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ajhuh-mdb LGTM with one optional nit
mvankeulen94
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for the speedy turnaround! added a couple small changes
source/faq.txt
Outdated
|
|
||
| To learn more about permissable reads and writes during synchronization, see :ref:`c2c-reads-and-writes`. | ||
| ``mongosync`` combines and reorders writes from the source to destination during | ||
| synchronization, and temporarily modifies collection characteristics. As a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"combines and reorders writes" -> link to https://www.mongodb.com/docs/cluster-to-cluster-sync/current/reference/mongosync/mongosync-behavior/#consistency
"temporarily modifies" -> link to https://www.mongodb.com/docs/cluster-to-cluster-sync/current/reference/mongosync/mongosync-behavior/#temporary-changes-to-collection-characteristics
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated!
source/faq.txt
Outdated
| synchronization, and temporarily modifies collection characteristics. As a | ||
| result, ``mongosync`` can't guarantee that the destination matches the source, | ||
| including a stale version of the source, at any point in time when the sync is | ||
| running. To safely accept traffic to the destination cluster, wait for the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"running" -> "running, even if the sync is paused"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
5579a4b to
233015c
Compare
mvankeulen94
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! lgtm
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.9 v1.9
# Navigate to the new working tree
cd .worktrees/backport-v1.9
# Create a new branch
git switch --create backport-612-to-v1.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6149617fb5573b0ec01baa07274d2b6d0a2f2c26
# Push it to GitHub
git push --set-upstream origin backport-612-to-v1.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.9Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.8 v1.8
# Navigate to the new working tree
cd .worktrees/backport-v1.8
# Create a new branch
git switch --create backport-612-to-v1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6149617fb5573b0ec01baa07274d2b6d0a2f2c26
# Push it to GitHub
git push --set-upstream origin backport-612-to-v1.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.8Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.10 v1.10
# Navigate to the new working tree
cd .worktrees/backport-v1.10
# Create a new branch
git switch --create backport-612-to-v1.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6149617fb5573b0ec01baa07274d2b6d0a2f2c26
# Push it to GitHub
git push --set-upstream origin backport-612-to-v1.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.10Then, create a pull request where the |
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback (cherry picked from commit 6149617)
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback (cherry picked from commit 6149617) Co-authored-by: Alison Huh <[email protected]>
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback
DESCRIPTION
STAGING
https://deploy-preview-612--docs-cluster-to-cluster-sync.netlify.app/faq/#can-i-perform-reads-or-writes-to-my-destination-cluster-while-mongosync-is-syncing-
JIRA
https://jira.mongodb.org/browse/DOCSP-47219